Publisher: | Dutton Books |
Copyright: | February 2019 |
Printing: | 2020 |
ISBN: | 0-7352-3190-7 |
Format: | Kindle |
Pages: | 339 |
org-beamer
workflow.
In my init.el I have
(defun org-babel-execute:stacker (body params)
(let* ((table '(? ?\n ?: ?/ ?? ?# ?[ ?] ?@ ?! ?$ ?& ??
?( ?) ?* ?+ ?, ?= ?%))
(slug (org-link-encode body table))
(simplified (replace-regexp-in-string "[%]20" "+" slug nil 'literal)))
(format "\\stackerlink %s " simplified)))
#+begin_src stacker :results value latex :exports both
(deffun (f x)
(let ([y 2])
(+ x y)))
(f 7)
#+end_src
#+RESULTS:
#+begin_export latex
\stackerlink %28deffun+%28f+x%29%0A++%28let+%28%5By+2%5D%29%0A++++%28%2B+x+y%29%29%29%0A%28f+7%29
#+end_export
\stackerlink
macro is probably fancier than needed. One could
just use \href
from hyperref.sty
, but I wanted to match the
appearence of other links in my documents (buttons in the margins).
This is based on a now lost answer from stackoverflow.com
;
I think it wasn't this one, but you get the main idea: use \hyper@normalise
.
\makeatletter
% define \stacker@base appropriately
\DeclareRobustCommand* \stackerlink \hyper@normalise\stackerlink@
\def\stackerlink@#1 %
\begin tikzpicture [overlay]%
\coordinate (here) at (0,0);%
\draw (current page.south west - here)%
node[xshift=2ex,yshift=3.5ex,fill=magenta,inner sep=1pt]%
\hyper@linkurl \tiny\textcolor white stacker \stacker@base?program=#1 ; %
\end tikzpicture
\makeatother
theme_ipsum_rc()
function by Bob Rudis from his hrbrthemes
package in a zero (added) dependency way. A simple example is (also
available as a demo inside the packages in the next update) contrasts
the default style (on left) with the one added by this package (on the
right):
The GitHub
repo also shows this little example: total dependencies of hrbrthemes
over what ggplot2
installs:
> db <- tools::CRAN_package_db()
> deps <- tools::package_dependencies(c("ggplot2", "hrbrthemes"), recursive=TRUE, db=db
> Filter(\(x) x != "ggplot2", setdiff(deps[[2]], deps[[1]]))
[1] "extrafont" "knitr" "rmarkdown" "htmltools"
[5] "tools" "gdtools" "extrafontdb" "Rttf2pt1"
[9] "Rcpp" "systemfonts" "gfonts" "curl"
[13] "fontquiver" "base64enc" "digest" "ellipsis"
[17] "fastmap" "evaluate" "highr" "xfun"
[21] "yaml" "bslib" "fontawesome" "jquerylib"
[25] "jsonlite" "stringr" "tinytex" "cachem"
[29] "memoise" "mime" "sass" "fontBitstreamVera"
[33] "fontLiberation" "shiny" "crul" "crayon"
[37] "stringi" "cpp11" "urltools" "httpcode"
[41] "fs" "rappdirs" "httpuv" "xtable"
[45] "sourcetools" "later" "promises" "commonmark"
[49] "triebeard"
>
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Rscript
. It allows for piping as well for shebang
scripting via #!
, uses command-line arguments more
consistently and still starts
faster. It also always loaded the methods
package which
Rscript
only began to do in recent years.
littler
lives on Linux and Unix, has its difficulties on macOS due to
yet-another-braindeadedness there (who ever thought case-insensitive
filesystems as a default were a good idea?) and simply does not exist on
Windows (yet the build system could be extended see RInside for
an existence proof, and volunteers are welcome!). See the FAQ
vignette on how to add it to your PATH
. A few examples
are highlighted at the Github repo:, as well
as in the examples
vignette.
This release contains a fair number of small changes and improvements
to some of the example scripts is run daily.
The full change description follows.
My CRANberries service provides a comparison to the previous release. Full details for the littler release are provided as usual at the ChangeLog page, and also on the package docs website. The code is available via the GitHub repo, from tarballs and now of course also from its CRAN page and viaChanges in littler version 0.3.19 (2023-12-17)
- Changes in examples scripts
- The help or usage text display for
r2u.r
,ttt.r
,check.r
has been improved, expanded or corrected, respectivelyinstallDeps.r
has a new argument for dependency selection- An initial 'single test file' runner
tttf.r
has been addedr2u.r
has two new options for setting / varying the Debian build version of package that is built, and one for BioConductor builds, one for a 'dry run' build, and a new--compile
optioninstallRSPM.r
,installPPM.r
,installP3M.r
have been updates to reflect the name changesinstallRub.r
now understands 'package@universe' toott.r
flips the default of the--effects
switch
install.packages("littler")
. Binary packages are
available directly in Debian as
well as (in a day or two) Ubuntu binaries at
CRAN thanks to the tireless Michael Rutter.
Comments and suggestions are welcome at the GitHub repo.
If you like this or other open-source work I do, you can sponsor me at
GitHub.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Thanks to my CRANberries, there is a diff to the previous release. The RProtoBuf page has copies of the (older) package vignette, the quick overview vignette, and the pre-print of our JSS paper. Questions, comments etc should go to the GitHub issue tracker off the GitHub repo. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in RProtoBuf version 0.4.21 (2022-12-13)
- Package now builds with ProtoBuf >= 22.x thanks to Matteo Gianella (#93 addressing #92).
- An Alpine 3.19-based workflow was added to test this in continuous integration thanks to a suggestion by Sebastian Meyer.
- A large number of old-style
.Call
were updated (#96).- Several packaging, dcoumentation and testing items were updated.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
as<>()
converter
from R values along with its companions wrap()
to return to
R, as well as more dedicated functions from and to .
This release addresses an issues Sebastian
reported a few hours and which is reported by newer, pickier compilers:
We need to include <cstdint>
so that
int64_t
is declared. CRAN was at its usual best
processing this efficiently including tests of the by now two reverse
dependencies. Twenty two minutes total, all automated:
The brief NEWS entry follows:
Courtesy of my CRANberries, there is a diffstat report relative to previous release. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in version 0.0.4 (2023-12-09)
- The
cstdint
header is now included (closes #1).
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
purple-discord
)amd64
, arm64
, armhf
, i386
, ppc64el
, riscv64
and s390
for Debian trixie, unstable and experimental, this is only around 500GB ie. less than 1%. Although the new service not yet ready for usage, it has already provided a promising outlook in this regard. More information is available on https://rebuilder-snapshot.debian.net and we hope that this service becomes usable in the coming weeks.
The adjacent picture shows a sticky note authored by Jan-Benedict Glaw at the summit in Hamburg, confirming Holger Levsen s theory that rebuilding all Debian packages needs a very small subset of packages, the text states that 69,200 packages (in Debian sid) list 24,850 packages in their .buildinfo
files, in 8,0200 variations. This little piece of paper was the beginning of rebuilder-snapshot and is a direct outcome of the summit!
The Reproducible Builds team would like to thank our event sponsors who include Mullvad VPN, openSUSE, Debian, Software Freedom Conservancy, Allotropia and Aspiration Tech.
[ ] introduce the concepts of Reproducible Builds, including best practices for developing and releasing software, the tools available to help diagnose issues, and touch on progress towards solving decades-old deeply pervasive fundamental security issues Learn how to verify and demonstrate trust, rather than simply hoping everything is OK!Germane to the contents of the talk, the slides for Vagrant s talk can be built reproducibly, resulting in a PDF with a SHA1 of
cfde2f8a0b7e6ec9b85377eeac0661d728b70f34
when built on Debian bookworm and c21fab273232c550ce822c4b0d9988e6c49aa2c3
on Debian sid at the time of writing.
[ ] today I hold in my hands the first two bit-identical LibreOffice rpm packages. And this is the success I wanted to share with you all today [and] it makes me feel as if we can solve anything.
esp32c3
microcontroller firmware reproducible with Rust, repro-env and Arch Linux:
I chose theesp32c3
[board] because it has good Rust support from theesp-rs
project, and you can get a dev board for about 6-8 . To document my build environment I usedrepro-env
together with Arch Linux because its archive is very reliable and contains all the different Rust development tools I needed.
dump
command and hopes that someone may be able to help.
amd64
, arm64
, i386
and armhf
architectures, data is collected from the Reproducible Builds testing framework is collected by this migration software even though, at the time of writing, it neither causes nor migration bonuses nor blocks migration. Indeed, the information only results are visible on Britney s excuses as well as on individual packages pages on tracker.debian.org.
.buildinfo
files
Back in 2017, Steve Langasek filed a bug against Ubuntu s Launchpad code hosting platform to report that .changes
files (artifacts of building Ubuntu and Debian packages) reference .buildinfo
files that aren t actually exposed by Launchpad itself. This was causing issues when attempting to process .changes
files with tools such as Lintian. However, it was noticed last month that, in early August of this year, Simon Quigley had resolved this issue, and .buildinfo
files are now available from the Launchpad system.
composer.lock
file, ensuring total reproducibility of the shipped binary file. Further details and the discussion that went into their particular implementation can be found on the associated GitHub pull request.
In addition, the presentation Leveraging Nix in the PHP ecosystem has been given in late October at the PHP International Conference in Munich by Pol Dellaiera. While the video replay is not yet available, the (reproducible) presentation slides and speaker notes are available.
7z
. [ ]RequiredToolNotFound
import. [ ]252
to Debian unstable. [ ]SOURCE_DATE_EPOCH
and CMake [ ], added iomart (ne Bytemark) and DigitalOcean to our sponsors page [ ] and dropped an unnecessary link on some horizontal navigation buttons [ ].
amber-cli
(date-related issue)bin86
(FTBFS-2038)buildah
(timestamp)colord
(CPU)google-noto-fonts
(file modification issue)grub2
(directory-related metadata)guile-fibers
(parallelism issue)guile-newt
(parallelism issue)gutenprint
(embedded date/hostname)hub
(random build path)ipxe
(nondeterministic behavoiour)joker
/ joker
kopete
(undefined behaviour)kraft
(embedde hostname)libcamera
(signature)libguestfs
(embeds build host file)llvm
(toolchain/Rust-related issue)nfdump
(date-related issue)ovmf
(unknown cause)quazip
(missing fonts)rdflib
(nondeterminstic behaviour)rpm
(toolchain)tigervnc
(embedded an RSA signature)whatsie
(date-related issue)xen
(time-related issue)policycoreutils
(sort-related issue)python-ansible-pygments
.bidict
.meson
.radsecproxy
.taffybar
.php-doc
.pelican
.maildir-utils
.openmrac-data
.vectorscan
.Priority: important
in a new package set. [ ][ ]pool_buildinfos
script to be re-run for a specific year. [ ]osuosl4
node [ ][ ] along with lynxis [ ].amd64
Ionos builders from 48 GiB to 64 GiB; thanks IONOS! [ ]arm64
architecture workers from 24 to 16 in order to improve stability [ ], reduce the workers for amd64
from 32 to 28 and, for i386
, reduce from 12 down to 8 [ ].cache_dir
size setting to 16 GiB. [ ]systemd-oomd
as it unfortunately kills sshd
[ ]debootstrap
from backports when commisioning nodes. [ ]live_build_debian_stretch_gnome
, debsums-tests_buster
and debsums-tests_buster
jobs to the zombie list. [ ][ ]jekyll build
with the --watch
argument when building the Reproducible Builds website. [ ]rc.local
s Bash syntax so it can actually run [ ], commenting away some file cleanup code that is (potentially) deleting too much [ ] and fixing the html_brekages
page for Debian package builds [ ]. Finally, diagnosed and submitted a patch to add a AddEncoding gzip .gz
line to the tests.reproducible-builds.org Apache configuration so that Gzip files aren t re-compressed as Gzip which some clients can t deal with (as well as being a waste of time). [ ]
#reproducible-builds
on irc.oftc.net
.
rb-general@lists.reproducible-builds.org
ARMA_IGNORE_DEPRECATED_MARKER
. So among the
over 1100 packages using RcppArmadillo
at CRAN, around a good dozen or
so were flagged in the upload but CRAN concurred and let the package
migrate to CRAN.
If you maintain an affected package, consider applying the patch or
pull request now. A simple stop-gap measure also exists by adding
-DARMA_IGNORE_DEPRECATED_MARKER
to
src/Makevars
as either PKG_CPPFLAGS
or
PKG_CXXFLAGS
to reactivate it. But a proper code update,
which is generally simple, may be better. If you are unsure, do not
hesitate to get in touch.
The set of changes since the last CRAN release follows.
Courtesy of my CRANberries, there is a diffstat report relative to previous release. More detailed information is on the RcppArmadillo page. Questions, comments etc should go to the rcpp-devel mailing list off the Rcpp R-Forge page. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in RcppArmadillo version 0.12.6.6.1 (2023-12-03)
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
lsos()
from a
StackOverflow question from 2009 (!!), the overbought/oversold
price band plotter from an older blog post, the market monitor
blogged about as well as the checkCRANStatus()
function
tweeted about by Tim
Taylor. And more so take a look.
This release brings a number of updates, including a rather nice
improvement to the market monitor
making updates buttery smooth and not flickering (with big
thanks to Paul Murrell who calmly pointed out once again that
base R does of course have the functionality I was seeking) as well as
three new functions (!!) and then a little maintenance on the
-Wformat
print format string issue that kept everybody
busy this week.
The NEWS entry follows.
Courtesy of my CRANberries, there is a comparison to [the previous release][previous releases]. For questions or comments use the the issue tracker at the GitHub repo. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in version 0.0.16 (2023-12-02)
- Added new function
str.language()
based on post by Bill Dunlap- Added new argument
sleep
inintradayMarketMonitor
- Switched to
dev.hold()
anddev.flush()
inintradayMarketMonitor
with thanks to Paul Murrell- Updated continued integration setup, twice, and package badges
- Added new function
shadowedPackages
- Added new function
limitDataTableCores
- Updated two
error()
calls to updated tidyCpp signature to not tickle-Wformat
warnings under R-devel- Updated two URL to please link checks in R-devel
- Switch two tests for variable of variable to
is.*
andinherits()
, respectively
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
-Wformat -Wformat-security
from the development branch of R. It also includes a new example snippet
illustrating creation of a numeric matrix.
The NEWS entry follows.
Thanks to my CRANberries, there is also a diffstat report for this release. For questions, suggestions, or issues please use the issue tracker at the GitHub repo. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in tidyCpp version 0.0.7 (2023-11-30)
- Add an example for a numeric matrix creator
- Update the continuous integration setup
- Accomodate print format warnings from r-devel
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
-Wformat -Wformat-security
so we injected a
number of "%s"
into Rf_error()
calls.
No new code or features. Full details below. And as a reminder, don t
use the old RcppClassic use Rcpp
instead.
Thanks to CRANberries, you can also look at a diff to the previous release. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in version 0.1.3 (2023-11-30)
- Update
Rf_error()
call to not tickle-Wformat
- Minor other packaging and continuous integration tweaks
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
-Wformat -Wformat-security
are enabled. This
amounted to re-generating RcppExports.cpp
under an updated
[Rcpp][rcpp] version. It also updates the package default help page by
removing some stubs that were not filled in.
The NEWS entry for this release follows.
Courtesy of my CRANberries, there is also a diffstat report. More detailed information is on the RcppSpdlog page, or the package documention site. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in RcppSpdlog version 0.0.15 (2023-11-29)
- Correct default package help page slighly
RcppExports.cpp
has been regenerated under an updated Rcpp to address a format string warning under R-devel
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
-Wformat -Wformat-security
are enabled. This
amounted to re-generating RcppExports.cpp
under an updated
Rcpp version. We also no longer set
C++14 explicitly as a compilation standard but rather determine at build
time if it is needed or not.
Courtesy of my CRANberries, there is a diffstat report for this release. See the project page and package documentation for more details, and more examples. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in version 0.0.9 (2023-11-29)
configure
now uses a new helper script to only set a compilation standard when needed for R versions older than 4.2.0- The file
RcppExports.cpp
was regenerated to avoid a string format warning from R-devel
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
-Wformat -Wformat-security
are enabled. This
amounted to re-generating RcppExports.cpp
under an updated
Rcpp version. We also no longer set
C++14 explicitly as a compilation standard.
The complete list changes for this release follows.
Courtesy of CRANberries, there is also a diffstat report relative to the previous release. More information is on the RcppQuantuccia page. Issues and bugreports should go to the GitHub issue tracker. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in version 0.1.2 (2023-11-29)
RcppExports.cpp
has been regenerated under an updated Rcpp to address a format string warning under R-devel- The compilation standard is no longer set to C++14
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
-Wformat -Wformat-security
. These are
frequently pretty simple changes as it was here: all it took was an call
to compileAttributes()
from an updated Rcpp version which now injects
"%s"
as a format string when calling
Rf_error()
.
The (very short) NEWS entry for this release follows.
Courtesy of my CRANberries, there is also a diffstat report for this release. For questions, suggestions, or issues please use the issue tracker at the GitHub repo. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in version 0.1.11 (2023-11-28)
RcppExports.cpp
has been regenerated under an update Rcpp to address a
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
printf
format string inaccuracies the compiler can detect
via the -Wformat -Wformat-security
flags. Two fairly
simplye ones were present here and have been addressed. In the time
since the last release about twenty months ago two or three other minor
packaging and setup details have also been taken care of, details are
below.
CRANberries also provides a diffstat report for the latest release. As always, feedback is welcome and the best place to start a discussion may be the GitHub issue tickets page. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in version 0.2.12 (2022-11-27)
- The continuous integration workflow received a trivial update, twice.
- The C++ compilation standard is now implicit per CRAN and R preference.
- The CITATION file format has been updated for the current usage.
- Two print format string issues reported by current R-devel have been addressed.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
printf
(or
alike) format checker found two more small issues. The run-time checker
for examples was unhappy with the callable bond example so we only run
it in interactive mode now. Lastly I had alread commented-out the
setting for a C++14 compilation (required by the remaining Boost
headers) as C++14 has been the default since R 4.2.0 (with suitable
compilers, at least). Those who need it explicitly will have to
uncomment the line in src/Makevars.in
. Lastly, the expand
printf
format strings also found a need for a small change
in Rcpp so the development version
(now 1.0.11.5) has that addressed; the change will be part of Rcpp
1.0.12 in January.
Courtesy of my CRANberries, there is also a diffstat report for the this release 0.4.20. As always, more detailed information is on the RQuantLib page. Questions, comments etc should go to the rquantlib-devel mailing list. Issue tickets can be filed at the GitHub repo. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in RQuantLib version 0.4.20 (2023-11-26)
- Correct three help pages with stray curly braces
- Correct two printf format strings
- Comment-out explicit selection of C++14
- Wrap one example inside 'if (interactive())' to not exceed total running time limit at CRAN checks
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Next.